home *** CD-ROM | disk | FTP | other *** search
- Path: news.interpath.net!mercury!softbase
- From: softbase@mercury.interpath.net (Scott McMahan - Softbase Systems)
- Newsgroups: comp.lang.c
- Subject: Re: Portability of code & skills (Beware of "C" Hackers etc)
- Date: 15 Mar 1996 13:29:59 GMT
- Organization: Interpath -- Providing Internet access to North Carolina
- Message-ID: <4ibrcn$a2r@news.interpath.net>
- NNTP-Posting-Host: mercury.interpath.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- Graham Perkins (grp@dmu.ac.uk) wrote:
- : Too true, too true. So if you want your new language to be a success,
- : then give it away for ten years, preferably with a free O.S. and all source
- : code as well. It's difficult to see many other reasons for widespread
- : adoption of C and Unix.
-
- I agree -- and if it wasn't for the rise of the PC and all of the C
- compilers for it, C may have died out or at least have been
- relegated to a niche. C just rode a wave of good fortune, and was
- chosen at strategic times for new platforms.
-
- : If I need to use an indexed file, with a primary index of unique composite
- : keys and two secondary indexes, one of which allows duplicates, and I want
- : the program to work on IBM, ICL, DEC mainframes and all DOS, Windows, Unix,
- : OS/2 boxes without editing one line of code or writing a make file, then
- : Cobol might be a better choice than C.
-
- But what's the COBOL compiler written in? The extremely high level
- COBOL source is portable because the system dependancies have been
- isolated in countless layers of code, mostly written in low level
- languages like C. I have a sneaking suspicion that MicroFocus COBOL, at
- least in UNIX, is written in C, since I can link in C routines and not
- have to link in the stdlib :) Like I said, there's a lot of low level
- code to be written no matter how high a level we want to operate at.
-
- Scott
-
-